Enablement of quasi time dependency in organizational hierarchies

ABSTRACT

Changes to a hierarchical organizational structure may be stored in different versions of a data structure depicting the hierarchical organizational structure. Each of these versions may include a validity period field representing a time period that the hierarchical organizational structure depicted in the version accurately reflects the organizational structure of the organization. Each of the versions may also be designated as active or inactive. In some instances, each of the versions may be designated as inactive except for a version that reflects the organizational structure of the organization at a particular time, which may change over time. Historical copies of versions may be stored and subsequently recalled to identify an organizational structure that was in effect at a particular time in the past. The recalled version may then be used to limit the results of a query to a selected node of the historical organizational structure.

RELATED APPLICATION

The present application claims the benefit of the Chinese Patent Application No. 201110351435.7 filed Nov. 8, 2011. The contents of which is incorporated herein by reference.

BACKGROUND

Many organizations have hierarchical organizational structures. For example, organizations may be structured into different parent and subsidiary companies. Hierarchical structures may also be implemented within individual companies as different divisions, departments, and groups within a company may be organized hierarchically. For example, groups and division may be organized by product and/or geographic area, so that similar groups of products may be part of a same division covering a particular geographic area. Hierarchies may also be used to organize data by type, function, or other criteria. For example, cost and/or profit centers of an organization may be organized into hierarchical groups in a tree structure according to a product type, geographic location, department organization, or other criteria. One or more nodes in the tree structure may then be selected to identify particular data of interest in a query or other data inquiry.

In many organizations, these hierarchical structures may change periodically as the organization reorganizes, merges, acquires another entity, or otherwise restructures. As the hierarchical structures change, the data structure in the organization's computing systems representing the hierarchy must also be updated. In many instances, the data structure is updated by overwriting the existing the data structure with the new hierarchical information. While the existing data structure may then accurately reflect an updated hierarchy, this procedure may make it difficult to retrieve and use past hierarchical information when querying historical data.

The inventors perceive a need to timely update hierarchical data structures as a hierarchical structure of an organization changes while preserving and making accessible historical hierarchical structures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary transitioning of an exemplary data structure between states in an embodiment.

FIG. 2 shows a first exemplary method in an embodiment of the invention.

FIG. 3 shows a second exemplary method in an embodiment of the invention.

FIGS. 4A to 4C show different exemplary interfaces in different embodiments relating to cost center hierarchies.

FIG. 5 shows an exemplary architecture in an embodiment of the invention.

DETAILED DESCRIPTION

In an embodiment of the invention, changes to a hierarchical organizational structure may be stored in different versions of a data structure depicting the hierarchical organizational structure. Each of these versions may include a validity period field representing a time period that the hierarchical organizational structure depicted in the version accurately reflects the organizational structure of the organization. The validity period may be unique in each version so that only one version of the organizational structure is valid at a time.

Each of the versions may also be designated as active or inactive. In some instances, each of the versions may be designated as inactive except for a version that reflects the organizational structure of the organization at a particular time, as indicated in the validity period field. The particular time may be a current time or some other identified past or future time. A processing device may check the validity period fields of each version to identify the version that accurately reflects the organizational structure of the organization at the identified time. The identified version may then be designated as the active version and the previously active version may be designated as inactive.

In some instance, a copy of each active version of the data structure may be kept for archival or other purposes. The copy may also include data identifying the period of time that the version was active. In some instances, this time period data may be similar to that included in the validity period field. In other instances, the time period data may be used to identify the time period that the version was actually designated as active.

The copies may later be used to retrieve and/or present historical organizational structure information. For example, if a user wants to analyze a specific set of past data, for example, through a query, the copies of the historical organizational structure that were active at that time may be retrieved and presented to the user to enable the user to select particular nodes in the structure or otherwise use the information contained in structure to analyze the past data.

FIG. 1 shows a transitioning of an exemplary data structure between active 110, inactive 140, and historic 170 states. A first active data structure 110 may show a hierarchical structure of an organization. The hierarchical structure may be any type of hierarchy in an organization, such as a management hierarchy, department hierarchy, cost/profit center hierarchy, parent/subsidiary company hierarchy, business process hierarchy, workflow/approval hierarchy, and so on.

This hierarchical structure may have a top level 1, sublevels 11 and 12, and items 111 and 121 assigned to each respective sublevel. Each of these different levels 1, 11, 12, and items 111 and 121 may be different nodes selectable by a user. In some embodiments, only certain nodes may be selectable, such as items 111 and 112, though in other embodiments, any of the nodes may be selectable.

A user may select one or more the nodes to limit a set of data to the data associated with the selected nodes and/or any nodes subordinate to the selected node. Thus, if a user were to select sub-level 11 in active data structure 110, in so doing the user may limit a set of data to that associated with the sub-level 11 node. In some instances, this limited set of data may also include data associated with sub-level 11's subordinate node item 111.

Each of the data structures may include an identifier 101. Organizations may have several different hierarchies for different departments, business processes, workflows, and so on. The identifier 101 may identify the specific hierarchy out of the several different type s of organizational hierarchies that the data structure represents. In this example, the identifier 101 indicates that the active data structure 110 is hierarchy type 001.

The active data structure 110 may be copied 181 to create one or more duplicate data structures that may be inactive 140. The duplicate data structures 140 may have an additional suffix 102 appended as part of the identifier 101 to differentiate them from each other and the active version 110. Each additional version of this data structure may have a unique suffix 102 appended to its identifier 101 to distinguish it from the other data structures.

Each duplicated data structure 140 may then be modified 182 to create a different version of the organizational structure. The modifications 182 shown in FIG. 1 include adding an additional item 122 subordinate to sub-level 11, removing sub-level 12 and item 121, and adding a new sub-level 13 subordinate to top level 1.

This modification to the organizational structure may take effect beginning in the first quarter of 2011, which may be specified in a validity period field 103 included in the data structure 140. The validity period field 103 may be used to ensure that the organization's computing systems seamlessly reflect this organizational structure change on the effective date during which the data structure is to become active. The validity period field 103 may include an identifier of a date the data structure 140 is to be activated and the organizational structure shown in the data structure is to take effect. In this example, the data structure 140 may be activated beginning at the start of the first quarter of 2011, which may also be when the new organizational structure shown is to take effect. In this example, the validity period “Q1-2011” representing the first quarter of 2011 may be included as part of the inactive data structure 140.

Once the first quarter of 2011 has begun 183, the active data structure 110 may be copied into a historical data structure 170. The historic data structure 170 may include a time period identifier 104 that identifies the time period that historic data structure 170 was active. The time period identifier 104 of each of the historic data structures 170 may then later be searched to identify the particular data structure that was active during a specified time.

After the active data structure 110 has been copied, the contents of the inactive data structure 140 having a validity period commencing in the first quarter of 2011 may then replace the contents of the formerly active data structure 110, so that the current organization structure may be presented as the active data structure.

FIG. 2 shows a first exemplary method in an embodiment of the invention. In box 201, an active version of a data structure depicting a hierarchical organizational structure may be copied. In box 202, the copied version may then be modified to reflect changes to the organization structure and the modified version may then be stored as an inactive version together with a validity period indicating when the inactive version is to be active. Once the validity period has been reached, in box 203, a copy of the active version of the data structure may be stored as a historical version together with a time period indicating a time the historical version was active. In box 204, the active version may be replaced with the stored inactive version at the validity date.

Later, responsive to a query specifying a second time period, in box 205, a version of the data structure active during the second time period may be identified. In box 206, the hierarchical organizational structure depicted in the identified version may then be presented to a user. In box 207, the user may also be presented with an option to select one or more nodes in the presented hierarchical organizational structure to complete the query. In some instances, the output of the query may be limited to data associated with these selected node(s).

In some instances, the validity period may be stored in two fields, a valid from field identifying a date the inactive version becomes active and a valid to field identifying a last date the inactive version remains active. In other instances, the validity period may initially only include a date that the inactive version becomes active. Once this date has been reached, the version may remain active until it is superseded by another inactive version that subsequently becomes active.

In some instances, the date the inactive version becomes active may be stored in the valid from field when the inactive version is stored and the last date the inactive version remains active may be stored in the valid to field when the last date occurs and the inactive version is no longer active. In other instances, the date the inactive version becomes active may be stored in the valid from field when the inactive version is stored and the last date the inactive version remains active may be stored in the valid to field when the inactive version is stored.

A version of the data structure that may be active during a time period specified in a query may be identified by comparing the time period specified in the query to the time periods of the data structure indicating the active period(s) of the data structure. Each inactive version of the data structure may also include a unique identifier that need not be visible to the user. The unique identifier may includes a different suffix for each version of the data structure. The suffix may, in some instances, remain constant as the version transitions between the active, inactive, and historical states. In an embodiment, the suffix may include the validity period or a portion thereof.

FIG. 3 shows a second exemplary process in an embodiment of the invention. In box 301, a time period encompassing an output of a query may be identified. In box 302, a type of hierarchical organizational structure associated with the query output may be identified. In box 303, the identified time period and the identified type of hierarchical organization structure may be compared to respective fields of a plurality of data structures specifying an active time period of each data structure and a type of hierarchical organizational structure in each data structure.

In box 304, the data structure depicting the identified type of hierarchical organizational structure that was active at the identified time period may be identified. In box 305, the hierarchical organizational structure depicted in identified data structure may be presented to a user. In box 306, the user may presented with an opportunity to select a node in the presented hierarchical organizational structure. Finally, in box 307, the output of the query may be limited to data associated with one or more of the nodes selected by the user.

FIGS. 4A to 4C show different exemplary interfaces in different embodiments relating to cost center hierarchies. FIG. 4A shows an exemplary interface for querying 400 different hierarchies stored in one or more data structures. The query interface 400 may include a search criteria section 404 where a user may specify one or more search criteria. The results of the query may be organized in a list and may include an area identifier 401, hierarchy identifier 101, and description 402. The area identifier 401 may identify a department, organization, or other entity to which a hierarchy included in the result list belongs. The one or more hierarchies in the result list may include a hierarchy identifier field 101 identifying the hierarchy included in the result list. A description of the hierarchy may also be provided in the description field 402. One or more of the hierarchies in the result list may be selected and copied to create an inactive copied version 403 of the hierarchy through a button or other medium.

FIG. 4B shows an exemplary interface for selecting a hierarchy version 412 to assign 410 to a particular area 401 and hierarchy 101. assigning a versions of a hierarchy 410. A query or search of different inactive hierarchy versions may be conducted and the results, including a validity period field 411, version identifier field 412, and description field 413, may be presented to the user. The user may then select one of the hierarchy versions and the version identifier 412 of the selected hierarchy version may be assigned 410 to the respective area 410 and hierarchy 101.

In other embodiments, an interface may be used to search for different hierarchy versions assigned 410 to particular areas 401 and/or hierarchy. In these other embodiments, a user may enter an area identifier 401, hierarchy identifier 101, hierarchy version, or other search criteria and a list of the active and/or inactive versions of the hierarchy may be presented. The hierarchies displayed in the list may include a validity period 411, hierarchy version identifier 412, and/or description 413 of the version. One or more of the hierarchy versions may then be selected to view and/or change the data associated with that version.

FIG. 4C shows an exemplary interface 430 to view and/or modify a hierarchy. The interface may include a hierarchy identifier 101, version identifier 412, and validity period 411 of the hierarchy. The interface 430 may also include one or more levels, including a top level 421 and one or more sub-levels 422, as well as one or more items 423. Levels and items may be added, changed, and moved to superordinate or subordinate positions in the hierarchy. Additional attributes or properties may also be added or changed with respect to the hierarchy in general, as well as with respect to the levels and items within the hierarchy.

FIG. 5 shows an exemplary architecture in an embodiment of the invention. Enterprising resource planning (ERP) system 510 may include a configuration arrangement 511, activation arrangement 512, and search arrangement 513.

The configuration arrangement 511 may enable the creation, modification, and/or configuration of hierarchical data structures. The configuration arrangement 511 may include hardware and other functionality to enable a user or program to create and/or modify hierarchical organizational structures and then save them as part of one or more data structures.

The activation arrangement 512 may identify and then activate different versions of the data structures during a validity period when the hierarchical organizational structure included in the data structure is effective and valid and/or deactivate a version of the data structure during a period when the when the hierarchical organizational structure included in the data structure is not in effect. The activation arrangement 512 may include hardware, such as processing device or comparator, as well as other functionality to enable the identification, activation, and/or deactivation of those data structures that should be activated and/or deactivated at a given moment.

The search arrangement 513 may identify a version of data structure active during a time period specified as part of a query and then present the hierarchical organizational structure of the identified version to a user to enable the user to a select one or more nodes in the hierarchical organizational structure in order to complete the query and/or limit the results of the query to the select node(s). The search arrangement 513 may include hardware, such as processing device or comparator, as well as other functionality to enable the identification of the active versions of a data structure during the time period specified as part of a query.

ERP system 510 may be connected to a network 550. Network 550 may include a LAN, WAN, bus, or the Internet. ERP system 510 may interface with other systems and components depending on the application. For example, a network/data storage device 560 may be used to store the different types of data structures, including active 561, inactive 562, and historic 563 versions of the data structures. The storage device 560 may be a part of the ERP system 510. In some embodiments the network storage device 560 may also be separate from the ERP system 510 but connected to it through network 550. The storage device 560 may contain a hard disk drive, flash memory, or other computer readable media capable of storing data. Other external systems and data sources 570 may also be connected to network 550. These other systems 570 may be used to supply additional data or information used by the ERP system 510, such as, for example, the initial data used to populate the generated data structures.

Each of the systems, clients, and devices in FIG. 5 may contain a processing device 502, memory 503 storing loaded data or a loaded data structure 505, and an communications device 504, all of which may be interconnected via a system bus. In various embodiments, each of the systems 510, 560, and 570 may have an architecture with modular hardware and/or software systems that include additional and/or different systems communicating through one or more networks. The modular design may enable a business to add, exchange, and upgrade systems, including using systems from different vendors in some embodiments. Because of the highly customized nature of these systems, different embodiments may have different types, quantities, and configurations of systems depending on the environment and organizational demands.

Communications device 504 may enable connectivity between the processing devices 502 in each of the systems and the network 550 by encoding data to be sent from the processing device 502 to another system over the network 550 and decoding data received from another system over the network 550 for the processing device 502.

In an embodiment, memory 503 may contain different components for retrieving, presenting, changing, and saving data. Memory 503 may include a variety of memory devices, for example, Dynamic Random Access Memory (DRAM), Static RAM (SRAM), flash memory, cache memory, and other memory devices. Additionally, for example, memory 503 and processing device(s) 502 may be distributed across several different computers that collectively comprise a system.

Processing device 502 may perform computation and control functions of a system and comprises a suitable central processing unit (CPU). Processing device 502 may include a single integrated circuit, such as a microprocessing device, or may include any suitable number of integrated circuit devices and/or circuit boards working in cooperation to accomplish the functions of a processing device. Processing device 502 may execute computer programs, such as object-oriented computer programs, within memory 503.

The foregoing description has been presented for purposes of illustration and description. It is not exhaustive and does not limit embodiments of the invention to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from the practicing embodiments consistent with the invention. For example, some of the described embodiments may include software and hardware, but some systems and methods consistent with the present invention may be implemented in software or hardware alone. 

We claim:
 1. A computer-implemented method comprising: copying an active version of a data structure depicting a hierarchical organizational structure; responsive to a modification to the hierarchical organizational structure depicted in the copied data structure, storing an inactive version of the modified structure with a validity period of the inactive version; responsive to reaching the validity period: storing a copy of the active version of the data structure as a historical version together with a first time period the active version was active; replacing, using a processing device, the active version of the data structure with the stored inactive version at the validity date; responsive to a query specifying a second time period: identifying a version of the data structure active during the second time period; presenting the hierarchical organizational structure depicted in the identified version to a user; and enabling the user to select a node in the presented hierarchical organizational structure to complete the query.
 2. The method of claim 1, wherein the validity period is stored in two fields, a valid from field identifying a date the inactive version becomes active and a valid to field identifying a last date the inactive version remains active.
 3. The method of claim 2, wherein the date the inactive version becomes active is stored in the valid from field when the inactive version is stored and the last date the inactive version remains active is stored in the valid to field when the last date occurs and the inactive version is no longer active.
 4. The method of claim 2, wherein the date the inactive version becomes active is stored in the valid from field when the inactive version is stored and the last date the inactive version remains active is stored in the valid to field when the inactive version is stored.
 5. The method of claim 1, further comprising, responsive to a plurality of modifications to the hierarchical organizational structure depicted in the copied data structure, storing a plurality of inactive versions of the modified structure, each including a unique validity period.
 6. The method of claim 5, further comprising comparing the second time period to the validity period in each of the data structures to identify the version of the data structure active during the second time period.
 7. The method of claim 5, wherein each inactive version includes a unique identifier that is not visible to the user.
 8. The method of claim 7, wherein the unique identifier includes a different suffix for each version of the data structure, each suffix identifying a date the respective version of the data structure is active.
 9. The method of claim 1, further comprising: enabling the user to select a plurality of nodes in the presented hierarchical organization structure, and limiting an output of the query to data associated with the selected nodes.
 10. The method of claim 1, further comprising: presenting a plurality of hierarchical organizational structures depicted in a plurality of identified versions to the user if more than one version of the data structure was active during the second time period; and enabling the user to select a node in any of the presented hierarchical organizational structures to complete the query.
 11. The method of claim 6, wherein responsive to the user selecting the node, the output of the query is limited to data associated with the selected node during the second time period.
 12. The method of claim 6, wherein responsive to the user selecting the node, the output of the query is limited to data associated with the selected node during a subset of the second time period when the presented hierarchical organizational structure containing the selected node was active.
 13. The method of claim 1, wherein the copy of the active version of the data structure stored as a historical version is stored before the active version of the data structure is replaced with the stored inactive version at the validity date.
 14. The method of claim 1, wherein the copy of the active version of the data structure stored as a historical version is stored after the active version of the data structure is replaced with the stored inactive version at the validity date and the stored inactive version of the data structure replacing the active version is stored as the historical version.
 15. A system comprising: a processing device; a storage device storing active, inactive, and historic versions of a data structure depicting a hierarchical organizational structure; a configuration arrangement to copy an active version of a data structure stored in the storage device and, responsive to a modification to the hierarchical organizational structure depicted in the copied data structure, store an inactive version of the modified structure with a validity period of the inactive version in the storage device; an activation arrangement to store a copy of the active version of the data structure as a historical version in the storage device together with a first time period the active version was active and, after reaching the validity period of the inactive version in the storage device, replace, using the processing device, the active version of the data structure with the stored inactive version; and a search arrangement to identify a version of the data structure active during a second time period specified in a query, present the hierarchical organizational structure depicted in the identified version to a user, and enable the user to select a node in the presented hierarchical organizational structure to limit a result of the query. 